WAP3GX WAP Gateway
The WAP3GX WAP Gateway is designed to meet the needs of multimedia applications, especially MMS (Multimedia Messaging Service) and Java downloads. With WAP providing the underlying protocol support for multimedia object delivery to mobile clients, the explosive growth of MMS services is placing heavy demands on conventional WAP gateways. The WAP3GX Gateway was designed to meet the needs of new MMS services, as well as legacy WAP applications.
The WAP3GX Gateway provides full WAP gateway support for WAP v1.1, v1.2, v1.2.1, and v1.3 WAP clients. The gateway also supports WAP v2.0 clients that utilize the low-level WAP protocols (WSP, WTP, WDP) for network connectivity.
Segmentation and re-assembly (SAR) is supported to provide support for larger object delivery to MMS (Multimedia Messaging Service) clients.
To implement WAP Push and MMS services in conjunction with WAP3GX, we recommend the use of the Now SMS/MMS Gateway. More information regarding the Now SMS/MMS Gateway can be found at http://www.nowsms.com.
The WAP3GX gateway can be installed on Windows NT, Windows 2000 and Windows XP platforms.
This help file provides details for configuring the WAP3GX gateway.
For automatic operation, WAP3GX is best installed as a service. Services are automatically started by Windows when the machine is started. When WAP3GX is configured to run as a service, it will always be available, as long as the machine running WAP3GX is powered on and connected to the network.
The “Service” tab of the configuration dialog provides setup options for installing WAP3GX as a service.
Check “Run as a service” to install and start the WAP3GX service.
The “Start” and “Stop” buttons can be used to start and stop the service.
To remove the WAP3GX service from the Windows services registry, uncheck “Run as a service”.
The “Service” tab of the configuration dialog also displays information about the status of the currently running service, indicating how long the service has been running, the number of currently active users, and the number of requests processed by the gateway.
The “Options” tab of the configuration dialog is used for setting some of the more commonly used configuration options for the gateway.
Check the “Use HTTP Proxy Server” checkbox if the gateway should forward all HTTP requests through an HTTP proxy server. Provide the IP address of the HTTP proxy server in the “HTTP Proxy Server” field. If a port number other than 80 is used by the proxy server, add a colon (:) and the port number to the proxy server IP address (e.g., 192.168.1.1:2080).
Older versions of the OpenWave/Phone.com browser installed on some phone models do not allow the home page to be set on the phone. For these legacy browsers, a default home page can be specified in the “Default home page for legacy browsers” field. Please specify a complete URL such as http://wap.mydomain.com/home.wml.
The “IP Address Restrictions” settings can be used to restrict access to the gateway to a pre-defined set of IP addresses. If “Restrict access to the Gateway” is checked, then only the IP addresses listed in the “Addresses Allowed to Use Gateway” table will be allowed to access the gateway. If “Restrict access to the Gateway” is not checked, then any device can connect to the gateway.
When adding IP Address restrictions, both an IP address and mask are specified. For example, to restrict access to only the IP address of 192.168.1.101, specify that address and a mask of 255.255.255.255. To restrict access to all IP addresses in the range 192.168.1.1 thru 192.168.1.254, specify any address within that range, and a mask of 255.255.255.0.
After entering an IP address and mask, click “Add” to add the entry to the list.
To remove an address from the allowed list, highlight the entry and click “Remove”.
Note that after making any configuration changes in this dialog, it is necessary to click “Apply” or “OK” for the changes to be saved.
The “MSISDN” tab of the configuration dialog allows the gateway to interface with a Radius accounting server that is integrated with the service provider’s data network. This allows the gateway to determine the MSISDN (phone number) of a connected user.
Note that this configuration is typically used only inside of a service provider’s data network, requiring that the WAP gateway be able to receive a Radius accounting feed from the provider’s dial-in server and/or GPRS network.
Check “Activate Radius Accounting for MSISDN Collection” to enable a Radius accounting server that is built into the WAP3GX gateway, and specify the port number on the local PC to be utilized. The default port number is 1813, although some older Radius services expect Radius accounting to listen to port 1646. You will also need to configure a “Shared Secret” that is common to the Radius server.
Once the “Radius accounting server” is enabled, the Radius servers on the service provider’s network should be configured to forward Radius Accounting packets to the WAP3GX gateway on the specified port.
Check “Activate Simple Radius Authentication Server” to enable a very simple Radius authentication server built into the WAP3GX gateway. This Radius authentication server accepts all logins, regardless of user name and password. This interface is provided for environments where a Radius proxy is unable to separate the Radius accounting and Radius authentication feeds. By default, Radius authentication services listen to port 1812, although some older Radius services expect Radius authentication services to listen to port 1645.
Check “Require MSISDN for all gateway connections” if you wish to only accept WAP connections where the MSISDN (phone number) of the device can be reliably determined. Note that this setting would normally only be used in an environment where the WAP3GX gateway is tightly integrated with the service provider network.
The gateway can forward the MSISDN of the WAP device to content servers via the “X-MSISDN:” HTTP header. Check “Forward MSISDN to Content Servers” to enable this capability. For privacy reasons, it is possible to explicitly list the content servers and/or domains that will receive the “X-MSISDN:” header. When a content domain is added to the list, a host name that exactly matches the content domain, as well as any host names within the content domain will receive the “X-MSISDN:” header. For example, if “now.co.uk” is added to the content domain list, the “X-MSISDN:” header would be forwarded to a host named “now.co.uk” as well as for “www.now.co.uk” and “mms.now.co.uk”. If you wish to have the “X-MSISDN” header forwarded to all content servers, define a content domain named “*”.
The WAP3GX gateway is licensed by active (or concurrent) users.
When the WAP3GX gateway is purchased, you will be provided with a serial number, user count and authorization code that must be entered into the “Serial #” tab of the configuration dialog. Enter this information and press “Add” to serialize the WAP3GX product.
Several additional configuration options may be applied by directly editing the WAPGW.INI file, located in the WAP3GX program directory.
The configuration settings described in this section may be entered into the WAPGW.INI file under the [WAPGW] section header.
SessionTimeout=####
This setting specifies a timeout value, in minutes, after which a gateway session will be automatically timed out. The default value is 10 minutes. Use caution when setting this value to lower values, as while most clients will automatically reconnect after a session timeout, some clients will report an error message.
DaysToKeepLogFile=####
This setting specifies the number of days to keep log files. The default value is 90 days. These are the WAPGW-YYYYMMDD.LOG files that the gateway maintains to track access. Note that the log files follow the standard format for a web server log file.
ResponseSizeLimits=Yes/No
When this setting is set to No, the gateway will not enforce any limits on the response size of data that is sent back to a mobile device. By default this setting is set to Yes, and the gateway will not sent any responses to a mobile device which exceed the response size that the device indicates that it will accept. The default setting is No.
AcceptAllMimeTypes=Yes/No
When this setting is set to Yes, the gateway will not reject responses from content servers that are in a MIME type that the client has not indicated that it will accept. By default this setting is set to No, and the gateway will return an error if a content server returns a MIME type that the client has not indicated that it will accept.
DefaultCharSet=####
This setting specifies a default Windows character set to be assumed for WAP content. By default, the gateway assumes that the UTF-8 character set is used, unless a “charset” header exists within a WML page. The mapping of MIME character sets to Windows character sets is automatically read from the Windows registry (HKEY_CLASSES_ROOT\MIME\Database\Charset). Additional character set mappings can be defined in a CHARSET.INI file, an example of which is shown below. Note that if the DefaultCharSet setting is used to specify a default character set, you must specify the Windows code page number, and not the MIME character set name.
[Charset]
us-ascii=1252
iso-8859-1=1252
iso-8859-2=1250
iso-8859-4=1257
iso-8859-5=1251
iso-8859-6=1256
iso-8859-7=1253
iso-8859-8=1255
iso-8859-9=1254
big5=950
big-5=950
gbk=936
gb2312=936
gb2312-80=936
shift-jis=932
shift_jis=932
iso-2022-kr=949
korean=949
ks_c_5601=949
KSC_5601=949
KSC5601=949
KSC-5601=949
WTPSarSegmentSize=####
This setting specifies the maximum segment size in bytes to be used in segmentation and reassembly (SAR) responses generated by the gateway. The default setting is 1400 bytes.
WTPSarWindowSize=####
This setting specifies the window size (number of packets sent without acknowledgement) to be used in segmentation and reassembly (SAR) responses generated by the gateway. The default setting is 3.